Skip to content

release: v0.1.2 - #49

Merged
prashar32 merged 1 commit into
mainfrom
release/v0.1.2
Jun 1, 2026
Merged

release: v0.1.2#49
prashar32 merged 1 commit into
mainfrom
release/v0.1.2

Conversation

@prashar32

Copy link
Copy Markdown
Owner

Release prep for v0.1.2 — the version markers that don't auto-update (§13). A low-risk polish patch ahead of launch; no breaking changes.

What's in v0.1.2

Fixed

Changed

Marker bumps

File Change
CHANGELOG.md [Unreleased] → dated [0.1.2]; fresh [Unreleased]; compare links
docs/VISION.md status → v0.1.2 (released)
internal/version/version.go default → 0.1.3-dev
sdks/python pyproject.toml + __init__.__version__0.1.2

After merge (tagging is manual)

  1. git checkout main && git pull first (the §13 guard — so the tag lands on the release commit, not a stale one).
  2. git tag -a v0.1.2 -m "v0.1.2" && git push origin v0.1.2 → release workflow builds + cosign-signs the multi-arch GHCR image and binaries.
  3. Verify: docker pull … && docker run ghcr.io/prashar32/riskkernel:0.1.2 version + cosign verify ….

This is the commit to launch on.

Roll [Unreleased] into [0.1.2] and bump version markers (CLAUDE.md §13):
- CHANGELOG: dated [0.1.2]; add the #30 audit-json-tags entry (credit @yzhkali,
  whose #35 merged without a changelog line); fresh empty [Unreleased]; links.
- docs/VISION.md status → v0.1.2 (released).
- internal/version/version.go default → 0.1.3-dev.
- sdks/python pyproject + __init__ __version__ → 0.1.2.

Contents: #34 (loop/time halt persists status), #30 (audit totals JSON keys),
#47 (MCP audits blocked tools), #48 (memory extensionless lookup).
@prashar32
prashar32 merged commit 1baa5d3 into main Jun 1, 2026
7 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant